Systems and methods for mobile application requests of physical facilities

ABSTRACT

Systems and methods are disclosed for enabling users to request information or services relating to a physical facility. One method includes receiving, from a device associated with a user, one or more of: a request to receive information about an asset or component of the facility, and a request to receive maintenance of an asset or component of the facility, wherein the request includes an identifier associated with the user and an identifier associated with the asset or component of the facility; accessing, based on the request, a database storing one or more user identifiers and one or more identifiers associated with a plurality of assets or components of the facility; and transmitting, to the device associated with the user, either a presentation of information about the asset or component of the facility, or a representation of a ticket for initiating maintenance of the asset or component of the facility.

TECHNICAL FIELD

Various embodiments of the present disclosure relate generally toincreasing productivity and accessibility of resources in a physicalfacility. More specifically, exemplary embodiments of the presentdisclosure relate to systems and methods for reducing an individual'stime spent on accessing information or making a request relating to afacility, and improving the accuracy and efficiency in fulfilling arequest via mobile communication.

BACKGROUND

In any facility, such as an office building, apartment building,commercial building (e.g., mall), sporting/music venue, or the like,people often find themselves desiring information about the facilityand/or desiring to submit a request relating to their interaction withthe facility. For example, people may desire information about wherevarious rooms, stores, or amenities are located. In addition, oralternatively, people might desire to submit various requests, such asrequests to have certain facilities repaired, or to reserve portions ofa facility for private use. As a result, building managers traditionallyerected physical directories, or distributed paper directories thatindividuals could consult to explore the facility. Also, managementwould traditionally implement procedures for making requests, such as byfilling out a request form with a facilities department, or submitting aconference room request form, etc.

In the context of commercial buildings, in particular, many employersimplement programs to train employees on how to submit request forms toaddress various issues. In addition to the time and expense spent onthese training programs, the actual request may take time beingsubmitted to the appropriate department and may lack sufficientspecificity for the request to be implemented. In the meantime, orinstead of sending the request, the employee may spend time attemptingto resolve the request on his or her own. This may result is a loss ofemployee productivity and/or an inaccurate or incomplete resolution tothe initial request. For example, an employee may wish to report aproblem with his or her printer to the information technology (IT)department of his or her employer. In order to do this, the employee mayhave to make a call, compose an email, and/or fill out a form making arequest; wait to communicate with an IT officer; and check back with theIT officer to obtain the status of the request. These steps may take asignificant amount of time, reducing employees' happiness andproductivity, and may result in the request not being timely completed.

Accordingly, a need exists for systems and methods for facilitatingaccurate, efficient and rapid processing of facilities requests. Thepresent disclosure is directed to, among other things, improving anexperience and reducing an amount of time spent on making a facilitiesrequest, and to improving the accuracy of fulfilling a request viamobile communication.

SUMMARY OF THE DISCLOSURE

According to certain embodiments, a computer-implemented method isdisclosed for enabling users to request information or services relatingto a physical facility, the method comprising: receiving, from a deviceassociated with a user, a request for information or services relatingto a physical facility, the request being one or more of: a request toreceive information about an asset or component of the facility, and arequest to receive maintenance of an asset or component of the facility,wherein the request includes an identifier associated with the user andan identifier associated with the asset or component of the facility;accessing, based on the received request, a database storing one or moreuser identifiers and one or more identifiers associated with a pluralityof assets or components of the facility; if the request is a request forinformation about an asset or component of the facility, generating apresentation of information about the asset or component, theinformation including data or photos stored in the database in relationto an identifier associated with the asset or component; if the requestis a request for maintenance of an asset or component of the facility,generating a ticket for initiating maintenance of the asset orcomponent, and storing the ticket in the database in relation to anidentifier associated with the asset or component; and transmitting, tothe device associated with the user, either the presentation ofinformation about the asset or component of the facility, or arepresentation of the ticket for initiating maintenance of the asset orcomponent of the facility.

According to certain embodiments, a system is disclosed for enablingusers to request information or services relating to a physicalfacility, the system comprising: a memory storage device storinginstructions for enabling users to request information or servicesrelating to a physical facility; and one or more processors configuredto execute the instructions to perform a method including: receiving,from a device associated with a user, a request for information orservices relating to a physical facility, the request being one or moreof: a request to receive information about an asset or component of thefacility, and a request to receive maintenance of an asset or componentof the facility, wherein the request includes an identifier associatedwith the user and an identifier associated with the asset or componentof the facility; accessing, based on the received request, a databasestoring one or more user identifiers and one or more identifiersassociated with a plurality of assets or components of the facility; ifthe request is a request for information about an asset or component ofthe facility, generating a presentation of information about the assetor component, the information including data or photos stored in thedatabase in relation to an identifier associated with the asset orcomponent; if the request is a request for maintenance of an asset orcomponent of the facility, generating a ticket for initiatingmaintenance of the asset or component, and storing the ticket in thedatabase in relation to an identifier associated with the asset orcomponent; and transmitting, to the device associated with the user,either the presentation of information about the asset or component ofthe facility, or a representation of the ticket for initiatingmaintenance of the asset or component of the facility.

According to one embodiment, a computer-readable medium is disclosedthat stores instructions that, when executed by a processor, cause theprocessor to execute a method for enabling users to request informationor services relating to a physical facility, the method comprising:receiving, from a device associated with a user, a request forinformation or services relating to a physical facility, the requestbeing one or more of: a request to receive information about an asset orcomponent of the facility, and a request to receive maintenance of anasset or component of the facility, wherein the request includes anidentifier associated with the user and an identifier associated withthe asset or component of the facility; accessing, based on the receivedrequest, a database storing one or more user identifiers and one or moreidentifiers associated with a plurality of assets or components of thefacility; if the request is a request for information about an asset orcomponent of the facility, generating a presentation of informationabout the asset or component, the information including data or photosstored in the database in relation to an identifier associated with theasset or component; if the request is a request for maintenance of anasset or component of the facility, generating a ticket for initiatingmaintenance of the asset or component, and storing the ticket in thedatabase in relation to an identifier associated with the asset orcomponent; and transmitting, to the device associated with the user,either the presentation of information about the asset or component ofthe facility, or a representation of the ticket for initiatingmaintenance of the asset or component of the facility.

Additional objects and advantages of the disclosed embodiments will beset forth in part in the description that follows, and in part will beapparent from the description, or may be learned by practice of thedisclosed embodiments. The objects and advantages of the disclosedembodiments will be realized and attained by means of the elements andcombinations particularly pointed out in the appended claims.

It is to be understood that both the foregoing general description andthe following detailed description are exemplary and explanatory onlyand are not restrictive of the disclosed embodiments, as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate various exemplary embodiments andtogether with the description, serve to explain the principles of thedisclosed embodiments.

FIG. 1 is a schematic diagram of an environment in which a user mayidentify and submit information related to a request for information orservices relating to a facility, according to an exemplary embodiment ofthe present disclosure.

FIG. 2 is a diagram of a system configured to enable users to identifyand submit information related to a request for information or servicesrelating to a facility, according to an exemplary embodiment of thepresent disclosure.

FIG. 3 is a schematic diagram of devices and indicia configured toenable users to identify and submit information related to a request forinformation or services relating to a facility, according to anexemplary embodiment of the present disclosure.

FIG. 4 is a flow diagram of an exemplary method for enabling users toidentify and submit information related to a request for information orservices relating to a facility, according to an exemplary embodiment ofthe present disclosure.

FIG. 5 is a screenshot of an exemplary mobile application for enablingusers to identify and submit information related to a request forinformation or services relating to a facility, according to anexemplary embodiment of the present disclosure.

FIG. 6 is a schematic diagram of a device and indicia for enabling usersto log-in to a mobile application for identifying and submittinginformation related to a request for information or services relating toa facility, according to an exemplary embodiment of the presentdisclosure.

FIGS. 7A-7D are screenshots of an exemplary mobile application forenabling users to identify and submit information related to a requestfor services relating to a facility, according to an exemplaryembodiment of the present disclosure.

FIGS. 8A-8E are screenshots of an exemplary mobile application forenabling users to identify and submit information related to a requestfor information relating to a facility, according to an exemplaryembodiment of the present disclosure.

DESCRIPTION OF THE EMBODIMENTS

Reference will now be made in detail to the exemplary embodiments of thedisclosure, examples of which are illustrated in the accompanyingdrawings. Wherever possible, the same reference numbers will be usedthroughout the drawings to refer to the same or like parts.

The present disclosure describes systems and methods for improving anindividual's or user's interaction with a facility and/or the people andservices associated with the facility; to reducing an amount of timespent on making a request; and to improving the accuracy of fulfilling afacilities-related request via mobile communication.

According to embodiments of the present disclosure, a user may use amobile device in communication with a wireless (Wi-Fi) router or awireless network that is in communication with the Internet to submit arequest for information or services. Although described herein as oftenpertaining to mobile devices and applications, it should be appreciatedthat the user may be operating any type of electronic device, whethermobile or not. In one embodiment, the user may submit the request to aserver by submitting an image of the user's identifier (e.g., ID,workplace badge, or building badge), and/or an asset's, component's, orentity's identifier to a server via the Internet or other network. Basedon the submitted identifier(s), the server may access a database toretrieve information regarding the user or entity associated with theidentifier, and identify the user's location based on the leveragedWi-Fi router or any other location-specific indicators. Alternatively,the location of the user may be identified using global positioning(GPS) coordinates of the user. The server may then prompt the user tosubmit a specific request based on the identified asset, component, orentity and/or location of the user. Once received, the server mayprocess the request and provide the user with information regarding thestatus of the request and may also update any databases and/or provideother users information regarding the request.

Referring now to the figures, FIG. 1 is a schematic diagram of anenvironment in which a user may identify and submit information relatedto a request for information or services relating to a facility,according to exemplary embodiments of the present disclosure.Specifically, FIG. 1 depicts and environment or facility 10, which maybe an office building, apartment building, commercial building (e.g.,mall), sporting/music venue, or the like. In one embodiment, environmentor facility 10 may be a workplace for a plurality of individuals orusers 12 (“people,” “individuals,” and “users” are used interchangeablyherein). In one embodiment, facility 10 may include one or more physicalspaces or rooms 11. Of course, it should be appreciated that facility 10may span any number of campuses, buildings, or cities. Facility 10 maybe a complex network of buildings for a multi-national corporationspread around the globe. Alternatively, facility 10 may be as small as asingle office.

As described above, facility 10 may be configured to enable users toidentify and submit information related to a request for information orservices relating to the facility. Accordingly, facility 10 may beprovided with one or more systems, devices, and indicia with which usersmay interact to submit requests for information or services from thosesystems and devices. For example, facility 10 may be provided with aserver system 32 provided in communication with one or more wirelessaccess points (WAPs) 34. Server systems 32 may include databases andprocessors configured to execute methods of enabling users to requestinformation or services relating to the facility. In addition, serversystems 32 may include any number of servers relating to the facilityand/or a business occupying the facility, such as helpdesk servers,Internet technology (IT) servers, human resources (HR) servers, employeeservers, document management servers, etc., as will be described in moredetail below.

In addition, one or more of users 12 (which may be owners and/oremployees of the business(es) occupying the facility 10) may eachpossess one or more electronic devices 14, for interacting with thefacility 10, and more specifically, for interacting with the serversystems 32 and/or wireless access points 34. In one embodiment, theusers' electronic devices 14 may be any type of mobile phone, personaldata assistant (PDA), tablet, personal computer (PC), an electronickiosk, or any other electronic device that may send and receiveinformation via a wireless network, such as over the Internet or alocal- or wide-area network (“LAN” or “WAN”). One or more of theelectronic devices 14 may include an optical component configured tocapture and/or recognize an image, and save and/or transmit the imagevia the Internet or a wireless network. For example, the opticalcomponent may be a camera, scanner, or any other suitable opticalcomponent. The electronic devices 14 may also be provided with aBluetooth or other radio frequency communication protocol, and/or a nearfield communication (NFC) device, for communicating with othersuitably-provisioned devices. Alternatively, or in addition to anoptical component, the electronic devices 14 may include one or moreaudio and/or video components configured to capture and/or recognize asound, series of sounds, and/or frame(s), and save and/or transmit thesound(s) and/or frame(s) via the wireless network. For example, an audiocomponent may include a microphone, or any other suitable audiocomponent, and a video component may include any type of camera.

In one embodiment, an optical component of each of electronic devices 14may be used to capture and/or recognize an identifier or indicia 16associated with any entity or asset of the facility 10, such as a user,a piece of equipment (e.g. printer 22, laptop 18, 24, tablet,television, desk, chair, etc.), a physical location (e.g. officebuilding, conference room 20, office 30, etc.), or any other entity. Theindicia 16 may be any machine-readable visual representation capable ofbeing captured and/or scanned by an optical component of an electronicdevice 14. For example, the indicia 16 may be a one, two, or threedimensional barcode, or any other visual identifier. Alternatively, theindicia 16 may include alphanumeric indicia, such as a name, roomnumber, serial number, etc., which the electronic device 14 or relateddevice or module may decode or otherwise recognize as indicative of theentity or asset of the facility 10. In one embodiment, the indicia 16may be associated with an entity or asset, and the association may besaved in retrievable memory, such as on a computer readable mediumassociated with server systems 32.

FIG. 2 is a diagram of a system 100 configured to enable users toidentify and submit information related to a request for information orservices relating to a facility, according to an exemplary embodiment ofthe present disclosure. In one embodiment, system 100 may include one ormore of HR server systems 102, information or Internet technology (IT)server systems 104, asset management server systems 106, and facilitiesserver systems 108. System 100 may further include a mobile facilitiesrequest server system 105, which may include one or more databases 110,processors 112, and/or user interface (UI) modules 114. System 100 mayfurther include or be provided in communication with a plurality of userdevices 116. As described above, user devices 116 may correspond to oneor more of user devices 14, which may be any type of mobile phone,personal data assistant (PDA), tablet, personal computer (PC), anelectronic kiosk, or any other electronic device that may send andreceive information via a wireless network, such as over the Internet ora local- or wide-area network. In addition, mobile facilities requestserver system 105 may correspond to server systems 32 provided incommunication with one or more wireless access points (WAPs) 34 within afacility 10, and users may interact with mobile facilities requestserver system 105 via any electronic devices 14, 116.

In one embodiment, a record of an association of an identifier of anasset or entity saved in memory may be located in one or more locationsbased on one or more characteristics of the entity. These locations maybe servers or other suitable devices configured to house and accesscomputer readable memory. For example, in an organization, such as alarge corporation, educational organization, government agency, etc., aseparate server may store information for a particular department. Inthe exemplary example shown in FIG. 2, an organization may have anetwork with separate servers, such as the Human Resources (HR) server102, configured to store, share, and update, information regardingemployees; the Information Technology server 104, configured to store,share, and update information regarding electronic equipment andrequests to repair electronic equipment; the assets server 106,configured to store, share, and update information regarding physicalproperty; and/or the facilities server 108, configured to store, share,and update information regarding various buildings and offices that arepart of the organization.

The servers may communicate with one or more servers, such as therequest server 105, having database(s) 110, processor(s) 112, and userinterface module(s) 114, via any local or wide area network. Thecommunication may be through wires or wirelessly via the Internet orlocal area network, or any other suitable means. The servers, such as arequest server 105, may receive and transmit information from devices,such as mobile devices 116 and other devices that may connect to therequest server 105. Each server, such as HR server 102, IT server 104,assets server 106, and/or building facilities server 108, maycommunicate directly with each other via the network 100 or through aserver or servers, such as the request server 105, or any other server.

In one embodiment, database(s) 110 may include any type of RAM or ROMembodied in a physical storage medium, such as magnetic storageincluding floppy disk, hard disk, or magnetic tape; semiconductorstorage such as solid state disk (SSD) or flash memory; optical discstorage; or magneto-optical disc storage. In addition, processor(s) 112may include one or more processors for processing data according toinstructions stored in the memory. The functions of the processor may beprovided by a single dedicated processor or by a plurality ofprocessors. Moreover, the processor may include, without limitation,digital signal processor (DSP) hardware, or any other hardware capableof executing software. The user interface module(s) 114 may include anytype or combination of programs for generating user interfaces displayedon devices 116, including but not limited to any input/output devices,such as a display monitor, touchpad, touchscreen, microphone, camera,keyboard, and/or mouse. In one embodiment, UI module(s) 114 may beconfigured to implement any number or type of user interfaces, whethertailored for desktop PC or mobile device implementation, including butnot limited to the user interfaces described below with respect to FIGS.5-8E.

In one embodiment, HR server systems 102 may be configured to implementany number or type of systems configured to manage people or employees,such as individual location information, demographic information,individual desk or office information, individual photographs,individual home addresses, individual equipment assignments, etc.Information or Internet technology (IT) server systems 104 may beconfigured to implement any number or type of systems configured tomanage and store individual IT assignments, such as computer, printer,or mobile device assignments, including device IDs (e.g., MAC ID orserial numbers), an IT profile, a search and/or browsing history, aclearance/accessibility level, etc. Asset management server systems 106may be configured to implement any number or type of systems configuredto manage and store information relating to any asset, equipment, orcomponent of a facility, such as printer, computer, wireless accesspoint, lab equipment, server, display, projector, television, or anyother device or system considered to be an asset of the facility.Facilities server systems 108 may be configured to implement any numberor type of systems configured to manage and store information relatingto a component of a facility, such as a facility floorplan, campus map,global map, facility map, equipment map, amenities map, facilityamenities map, and so on. Any one or more of HR servers 102, IT servers104, asset servers 106, and facilities servers 108 may be configured tostore information relating to requests, generate presentations ofinformation, generate tickets for initiating the performance of serviceor maintenance, and so on.

In one embodiment, mobile facilities request server system 105 may beconfigured to communicate with one or more of HR server systems 102,information or Internet technology (IT) server systems 104, assetmanagement server systems 106, and facilities server systems 108 toperform the methods described herein, whether by wired or wirelesscommunications. For example, mobile facilities request server system 105may include one or more translators or application programminginterfaces (APIs) configured to communicate with various types of knownservers systems for managing assets, equipment, people, facilities, andso on. In addition, mobile facilities request server system 105 may beconfigured to facilitate interaction between user devices 116 and thoseserver systems 102-108, whether directly or indirectly, and whetherthrough the Internet or over local wireless networks.

As described above, in one embodiment, user devices 116 may beconfigured to interact with a facility 10 through, among other means,imaging of indicia 16 (FIG. 1). Accordingly, in one embodiment, system100 of FIG. 2 may be configured to operate in conjunction with exemplaryindicia depicted in FIG. 3. FIG. 3 is a schematic diagram of devices andindicia 200 configured to enable users to identify and submitinformation related to a request for information or services relating toa facility, according to an exemplary embodiment of the presentdisclosure.

For example, as shown in FIG. 3, in one embodiment, a two-dimensionalbarcode 202 a may be displayed on an ID badge 202 of a user, such as anemployee of a company, or a student at an educational institution, orany other organization. Also shown in FIG. 3 are other examples ofidentifiers or indicia, such as a one-dimensional bar code 204 adisplayed on a surface of a piece of equipment, such as a printer 204,and a two-dimensional bar code 206 a displayed on a name plate 206 of auser's office. As shown in FIG. 3, a mobile device 208 containing anoptical component, e.g., a camera, may be used to capture an image ofthe identifier or indicia 202 a, 204 a, 206 a, associated with therespective entity and transmit the image to a server for processing arequest. Alternatively, device 208 may read and decode any indicia, orotherwise locally obtain one or more data elements or unique IDs fromthe indicia. In one embodiment, a user may scan his or her own badge202, containing indicia 202 a (e.g., a two-dimensional barcode or QRcode) to log-in to a mobile application on the user's device 116. Forexample, the indicia 202 a may contain a unique ID associated with theuser's identity, whether in an HR database such as in an HR server 102,or otherwise. The user may then, once logged-in, easily interact,directly or indirectly, with assets and/or components of a facility 10(e.g., assets 204 and/or indicia 206 of facilities) to make certainrequests for information or services relating to those assets orfacilities.

FIG. 4 is a flow diagram of an exemplary method for enabling users toidentify and submit information related to a request for information orservices relating to a facility, according to an exemplary embodiment ofthe present disclosure. Specifically, FIG. 4 is a flowchart of a method300 for fulfilling a request, according to an exemplary embodimentconsistent with embodiments of the present disclosure. At step 302, aserver, such as request server 105, may receive, from a user via amobile device 116, a communication regarding an entity. For example, thecommunication may be an image of the user's identification bar code 202a on the user's identification badge 202. In addition, or alternatively,the communication may be an image of an identifier associated with apiece of equipment, other user, or office, for example, an image of thebar code 204 a of a printer 204, or bar code 206 a of a room 206, or anyother identifier.

Based on the image of the identifier received from the user's mobiledevice, the server, such as a request server 105, may access a databaseto retrieve information regarding the entity associated with theidentifier (step 304). For example, the request server 105 maycommunicate with the HR server 102 to access information regarding theuser, based on the user's identification bar code 202 a.

At step 306, the request server 105 may determine the location of themobile device 116 from which the image was sent. This locationdetermination may be based, in part, on receiving information regardingthe location of the wireless connection point that the mobile device 116connected to in order to communicate with the request server 105. Forexample, if the user of the mobile device 116 accessed the network 100by connecting to a stationary wireless port, such as a wireless routerconnected to the network, the server may determine that the user is inclose proximity to the stationary wireless port. In addition to, oralternatively, the request server may determine the location of the userusing global positioning (GPS) data of the mobile device 116. Thelocation of the user may be used by the request server 105 to betterfacilitate the user's request.

At step 308, the request server 105 may prompt the user to submit aspecific request, based on the information retrieved from the otherservers. For example, in a manner as described above, the request server105 may determine that the user is a new employee and has sent an imageof an identifier associated with a printer. Based on this information,the user may send a message to the user via the mobile device 116, inthe form of a text, email or other form of communication prompting theuser to submit a request, and may provide a list of options, such as ifthe user would like to connect to the printer, if the user would like toreport a problem with the printer, if the user would like furtherinformation about the printer etc. The user may then submit a request inresponse to the prompt via the mobile device 116 connected to thenetwork 100.

At step 310, the request server may receive the request and process it,such as sending the request to the relevant entity to fulfill therequest and or retrieve any information in the request for the relevantdatabase. Prior to processing the request, the request server 105 maydetermine if the user is authorized to make the request. For example,the request server 105 may retrieve information about the user from aserver, such as a HR server 102, based on the user's identifier. The HRserver 102 may include information regarding the type of requests thatuser is authorized to make. For example, the HR server 102 may includevarious levels of security or permissions associated with each user andwhat type of requests the user may make using the network. Any suitabletype or restrictions and categories may be associated with each user.These restrictions may be set by an administrator or any other suitableentity. For example, the request server may retrieve information aboutthe user from the HR server 102 and determine, based on thisinformation, that the user is not authorized to make the request. Inthis case, the request server 105 may send a communication to the user'smobile device 116, informing the user that they are not authorized tomake the request. If the request server determines 105, based oninformation retrieved from the database(s), that the user is authorizedto make the request, then the request may proceed to being processed atstep 310.

Step 310 may include steps of sending and receiving communications, suchas messages, information, instructions, etc., to servers, mobiledevices, other users, etc., in order to fulfill the request. Forexample, referring to the previous example, if the user requests, viathe mobile device 116, to print to a printer 204 connected to thenetwork, the request server 105 may communicate with the IT server 104and the assets server 106 to connect the mobile device 116 to theprinter, 204, via the network.

At step 312, the request server may check the status of the request bycommunication with the relevant server and then provide a statuscommunication to the user's mobile device 116 regarding the request.Once the request has been completed, the request server 105 may send acommunication to the mobile device 116 at step 314, informing the userthat the request has been completed. At step 316, the request server 105may update any databases based on the fulfilled request.

In an example, in accordance with the present disclosure, the user mayprovide a request prior to sending an image of an identifier; therefore,the step or prompting the user for a request may be skipped. In anotherexample, in accordance with the present disclosure, the user may providea request at the same time as sending an image of the identifier andtherefore the step of prompting the user for a request may be skipped.

FIG. 5 is a screenshot of an exemplary mobile application for enablingusers to identify and submit information related to a request forinformation or services relating to a facility, according to anexemplary embodiment of the present disclosure. Specifically, FIG. 5depicts a mobile application interface 500 by which a user may submitinformation related to a request for information or services relating toa facility. For example, a user may be presented with one or more userelements 502, 504, 506, 508, which may be hyperlinks, buttons, or othermobile application elements that a user can select to initiate making arequest for information or services. For example, as shown in FIG. 5, auser may manipulate user element 502 to issue a request for servicerelating to a “PROBLEM WITH EQUIPMENT.” The user may manipulate userelement 504 to issue a request for information relating to “MYNEIGHBORHOOD.” The user may manipulate user element 506 to issue arequest to “FIND STUFF AROUND ME.” The user may manipulate user element508 to issue a request for a “CONFERENCE ROOM HELPER.” Of course, theindicated user elements are only exemplary of the many types of requestsfor information or services that may be implemented by a mobileapplication of a user device 116. When a user selects or otherwisemanipulates one or more of user elements 502-508, the user's mobiledevice 116 may update its display with another presentation ofinformation, forms, data, request options, etc. to further facilitatethe user's request for information or services. In one embodiment, acombination of user elements 502-508 available/presented to a user maydepend on a user's identity. Alternatively, a sub-menu or next screendisplayed upon a user's selection of one of user elements 502-508 maydepend on a user's identity.

Accordingly, FIG. 6 is a schematic diagram of a device and indicia forenabling users to log-in to a mobile application for identifying andsubmitting information related to a request for information or servicesrelating to a facility, according to an exemplary embodiment of thepresent disclosure. Specifically, FIG. 6 depicts an embodiment in whicha user may possess an ID card or badge 602 having, for example, aphotograph, avatar, or other optional image 604, along with amachine-readable identifier or indicia 606. In one embodiment, asdescribed above with respect to FIG. 3 (indicia 202 a of badge 202), theindicia 606 may be a one or two dimensional barcode, such as, forexample, a QR code. Thus, a user may operate his or her electronicdevice 116 (and a mobile application thereon) to capture an image of theindicia 606, or otherwise decode the indicia 606, to obtain at least auser identifier associated with the depicted user 604. Accordingly, amobile application operating on electronic device 116 may identify auser (e.g., through the decoded unique ID), authenticate the user of themobile application as being the owner of the electronic device 116, andtailor one or more presentations of data or generating of tickets basedon the authenticated user identity.

FIGS. 7A-7D are screenshots of an exemplary mobile application forenabling users to identify and submit information related to a requestfor services relating to a facility, according to an exemplaryembodiment of the present disclosure. Specifically, FIG. 7A is ascreenshot of an exemplary mobile application interface 700 by which auser may submit a request for service relating to an asset or componentof a facility. For example, a user may submit a request for servicerelating to a printer, fax machine, telephone, furniture, lab equipment,machine, tool, or any other asset within a facility. As shown in FIG.7A, in one embodiment, a user may manipulate various user interfaceelements of interface 700 to generate and submit a request, fortransmission through the user's electronic device 116.

For example, in one embodiment, the user may select element 702 to scanor otherwise image or decode machine-readable indicia printed on anasset. For example, the user may scan a barcode or QR code printed on alabel of a piece of equipment, as shown with respect to the printer ofFIG. 3. Alternatively, the user may select user element 704 to manuallyenter an asset tag or unique ID number using an alphanumeric keyboard ofthe user's device. In addition, as shown in FIG. 7A, a user maymanipulate user element 706 to indicate a problem type, such as amalfunction of or damage to the selected equipment or asset. The usermay also or alternatively type in a narrative description of a problemusing user element or form 708.

As shown in FIG. 7B, once a user has either successfully scanned anequipment or asset indicia, or manually entered an equipment or assetunique ID, the interface 700 may display profile information 710associated with the equipment or asset. For example, profile information710 may include a description of the asset or equipment; the name,number, ID, etc. of the individual to whom the asset or equipment isoptionally assigned; a physical location of the asset or equipment(e.g., address, building number, room number, lat/long coordinates,etc.); and/or a phone number associated with a location or owner of theequipment or asset. As shown at ticket creation window 712, a user mayenter a problem type, problem details, etc., and then manipulate userelement 714 to snap a photograph of the equipment or asset to assist inlocating, diagnosing, and/or repairing the subject asset or equipment.For example, as shown in FIG. 7C, the user may have uploaded aphotograph 716 of a particular piece of equipment or asset for which theuser is requesting information or service.

Accordingly, based on a user's interaction with the interfaces and userelements described and depicted with respect to FIGS. 7A-7C, system 100of FIG. 2 may operate programmed instructions to execute a method ofprocessing the user's request for service and/or generating a ticket toperform the user's requested service. For example, server systems 105may receive the request from a user device 116, store the receivedinformation in databases 110, execute processors 112 to interact withone or more of HR server systems 102, IT server systems 104, assetserver systems 106, and facilities server systems 108 to obtain relevantinformation from those systems, and generate suitable requests relatingto the equipment. In addition, UI module(s) 114 may update a display ofinformation, repair tickets, etc. on a display of a user's electronicdevice 116. For example, as shown in FIG. 7D, processor(s) 112 mayinteract with one or more of HR server systems 102, IT server systems104, asset server systems 106, and facilities server systems 108 togenerate a ticket, and interact with UI module(s) 114 to present aticket and/or ticket number 718 to a user that requested the relatedservice.

FIGS. 8A-8E are screenshots of an exemplary mobile application forenabling users to identify and submit information related to a requestfor information relating to a facility, according to an exemplaryembodiment of the present disclosure. Specifically, FIG. 8A depicts anexemplary mobile application interface 800 by which a user may submit arequest for information relating to an asset or component of a facility.For example, a user may submit a request for information relating toavailable building amenities, equipment, directions, policies, etc. Asshown in FIG. 8A, in one embodiment, a user may manipulate various userinterface elements of interface 800 to generate and submit a request,for transmission through the user's electronic device 116. For example,a user may be presented with one or more user elements 804, which may behyperlinks, buttons, or other mobile application elements that a usercan select to initiate making a request for information. For example, asshown in FIG. 8A, a user may manipulate one or more of user elements 804to issue requests for information relating to gyms, help centers,receptionists, game rooms, conference rooms, and so on. In oneembodiment, the building amenities displayed in relation to userelements 804 may be sorted based on their respective location relativeto a detected location of the user (i.e., with the closest buildingamenities listed first).

As shown in FIG. 8B, in one embodiment, the mobile application interface800 may display indicia 806 representing individuals within somepredetermined proximity of a detected location of the user. In oneembodiment, the individuals displayed in relation to user elements 806may be sorted based on their respective location relative to a detectedlocation of the user (i.e., with the closest individuals listed first).In one embodiment, the displayed indicia 806 may include a name, officelocation, building location, phone number, or any other usefulinformation stored in relation to the individual.

As shown in FIG. 8C, in one embodiment, the mobile application interface800 may display indicia 808 representing amenities within somepredetermined proximity of a detected location of the user. For example,the amenities may include break areas, cafeterias, conference rooms,copy rooms, restrooms, vending areas, printers, etc. In one embodiment,the amenities displayed in relation to user elements 808 may be sortedbased on their respective location relative to a detected location ofthe user (i.e., with the closest building amenities listed first). Inone embodiment, the displayed indicia 808 may include a name, officelocation, building location, phone number, or any other usefulinformation stored in relation to the amenity.

As shown in FIG. 8D, in one embodiment, the mobile application interface800 may display indicia 810 representing facilities, rooms, or officeswithin some predetermined proximity of a detected location of the user.For example, the facilities may include any type of office or conferenceroom. In one embodiment, the facilities displayed in relation to userelements 810 may be sorted based on their respective location relativeto a detected location of the user (i.e., with the closest buildingfacilities listed first). In one embodiment, the displayed indicia 810may include a name, office location, building location, phone number, orany other useful information stored in relation to the facilities.

In one embodiment, as shown in FIG. 8E, a user may be able to manipulatethe mobile application operating on the user's electronic device 116 to“check-in” to any desired location. For example, the user may publicallyor semi-publically associate himself or herself with some particularlocation by scanning a barcode (e.g., by manipulating user element 812of interface 800) known to have a particular location. For example, theuser may check-in to a particular office or conference room by scanninga barcode or QR code on the door or wall of that room. Alternatively,the user may check-in to the office or room by scanning a barcode or QRcode on a piece of equipment in that room.

The many features and advantages of the disclosure are apparent from thedetailed specification, and thus, it is intended by the appended claimsto cover all such features and advantages of the disclosure which fallwithin the true spirit and scope of the disclosure. Further, sincenumerous modifications and variations will readily occur to thoseskilled in the art, it is not desired to limit the disclosure to theexact construction and operation illustrated and described, andaccordingly, all suitable modifications and equivalents may be resortedto, falling within the scope of the disclosure.

Other embodiments of the disclosure will be apparent to those skilled inthe art from consideration of the specification and practice of theinvention disclosed herein. It is intended that the specification andexamples be considered as exemplary only, with a true scope and spiritof the invention being indicated by the following claims.

1-20. (canceled)
 21. A computer-implemented method for enabling users torequest information or services relating to a physical facility, themethod comprising: receiving an identifier of an asset or componentwithin the physical facility, from a device that is associated with auser; accessing, based on the received identifier of the asset orcomponent within the physical facility, a database to retrieveinformation about the asset or component; displaying to the user one ormore fields of information to be entered by the user, the one or morefields of information being selected for display based on the receivedidentifier, a location of the user, and an identity of the user, for theuser to submit a request; receiving, from the device associated with theuser by way of the one or more fields of information, a request forinformation or services relating to the physical facility; if therequest is a request for information about an asset or component of thephysical facility, generating a presentation of information about theasset or component, based on a detected location of the deviceassociated with the user and the received identifier; if the request isa request for maintenance of an asset or component of the physicalfacility, generating a ticket for initiating maintenance of the asset orcomponent, and storing the ticket in the database in relation to anidentifier associated with the asset or component; and transmitting, tothe device associated with the user, either the presentation ofinformation about the asset or component of the physical facility, or arepresentation of the ticket for initiating maintenance of the asset orcomponent of the physical facility.
 22. The method of claim 21, furthercomprising: generating the presentation of information or the ticket forinitiating maintenance based on a detected location of the deviceassociated with the user, wherein the detection is performed based onone or more of: GPS data obtained from the device, radio frequency dataobtained from the device, identification information obtained from thedevice, or a triangulation of the device by wireless access points inthe physical facility.
 23. The method of claim 21, wherein theinformation about an asset or component of the physical facilityincludes data or photos stored in the database in relation to anidentifier associated with the asset or component based on the receivedidentifier and the detected location of the device within the physicalfacility.
 24. The method of claim 21, wherein the request forinformation is a request for information about facility amenities andlocations of facility amenities within the physical facility.
 25. Themethod of claim 21, wherein the request for information is a request forinformation about: locations of individuals within the physical facilityor locations of individuals' offices or desks within the physicalfacility.
 26. The method of claim 21, wherein the request forinformation includes a location of the user within the facility, and therequest for information is request for information about locations ofone or more amenities within the facility, each amenity being one of abreak area, cafeteria, conference room, copy room, restroom, vendingarea, or gym, relative to the location of the user and, wherein theinformation about the located amenities is displayed in a sorted orderaccording to a proximity of each amenity to the location of the user.27. The method of claim 21, wherein the request for information includesan identifier associated with the asset or component of the facilitythat is captured by the device associated with the user.
 28. The methodof claim 21, wherein the request for information includes an identifierassociated with an office or desk of an individual that resides or worksin the physical facility.
 29. The method of claim 21, wherein therequest to receive maintenance of an asset or component of the facilityincludes a photograph of the asset or component of the facility, thephotograph being captured by the device associated with the user. 30.The method of claim 21, wherein the request to receive maintenance of anasset or component of the facility includes a selection of a type ofproblem experienced by the asset or component and an identifierassociated with the asset or component.
 31. A system for enabling usersto request information or services relating to a physical facility, thesystem comprising: a memory storage device storing instructions forenabling users to request information or services relating to a physicalfacility; and one or more processors configured to execute theinstructions to perform a method including: receiving an identifier ofan asset or component within the physical facility, from a device thatis associated with a user; accessing, based on the received identifierof the asset or component within the physical facility, a database toretrieve information about the asset or component; displaying to theuser one or more fields of information to be entered by the user, theone or more fields of information being selected for display based onthe received identifier, a location of the user, and an identity of theuser, for the user to submit a request; receiving, from the deviceassociated with the user by way of the one or more fields ofinformation, a request for information or services relating to thephysical facility; if the request is a request for information about anasset or component of the physical facility, generating a presentationof information about the asset or component, based on a detectedlocation of the device associated with the user and the receivedidentifier; if the request is a request for maintenance of an asset orcomponent of the physical facility, generating a ticket for initiatingmaintenance of the asset or component, and storing the ticket in thedatabase in relation to an identifier associated with the asset orcomponent; and transmitting, to the device associated with the user,either the presentation of information about the asset or component ofthe physical facility, or a representation of the ticket for initiatingmaintenance of the asset or component of the physical facility.
 32. Themethod of claim 31, further comprising: generating the presentation ofinformation or the ticket for initiating maintenance based on a detectedlocation of the device associated with the user, wherein the detectionis performed based on one or more of: GPS data obtained from the device,radio frequency data obtained from the device, identificationinformation obtained from the device, or a triangulation of the deviceby wireless access points in the physical facility.
 33. The system ofclaim 31, wherein the information about an asset or component of thephysical facility includes data or photos stored in the database inrelation to an identifier associated with the asset or component basedon the received identifier and the detected location of the devicewithin the physical facility.
 34. The system of claim 31, wherein therequest for information is a request for information about facilityamenities and locations of facility amenities within the physicalfacility.
 35. The system of claim 31, wherein the request forinformation is a request for information about: locations of individualswithin the physical facility or locations of individuals' offices ordesks within the physical facility.
 36. The system of claim 31, whereinthe request for information includes a location of the user within thefacility, and the request for information is request for informationabout locations of one or more amenities within the facility, eachamenity being one of a break area, cafeteria, conference room, copyroom, restroom, vending area, or gym, relative to the location of theuser and, wherein the information about the located amenities isdisplayed in a sorted order according to a proximity of each amenity tothe location of the user.
 37. The system of claim 31, wherein therequest for information includes an identifier associated with the assetor component of the facility that is captured by the device associatedwith the user.
 38. The system of claim 31, wherein the request toreceive maintenance of an asset or component of the facility includes aphotograph of the asset or component of the facility, the photographbeing captured by the device associated with the user.
 39. The system ofclaim 31, wherein the request to receive maintenance of an asset orcomponent of the facility includes a selection of a type of problemexperienced by the asset or component and an identifier associated withthe asset or component.
 40. A computer-readable medium storinginstructions that, when executed by a processor, cause the processor toexecute a method for enabling users to request information or servicesrelating to a physical facility, the method comprising: receiving anidentifier of an asset or component within the physical facility, from adevice that is associated with a user; accessing, based on the receivedidentifier of the asset or component within the physical facility, adatabase to retrieve information about the asset or component;displaying to the user one or more fields of information to be enteredby the user, the one or more fields of information being selected fordisplay based on the received identifier, a location of the user, and anidentity of the user for the user, to submit a request; receiving, fromthe device associated with the user by way of the one or more fields ofinformation, a request for information or services relating to thephysical facility; if the request is a request for information about anasset or component of the physical facility, generating a presentationof information about the asset or component, based on the receivedidentifier and a detected location of the device within the physicalfacility; if the request is a request for maintenance of an asset orcomponent of the physical facility, generating a ticket for initiatingmaintenance of the asset or component, and storing the ticket in thedatabase in relation to an identifier associated with the asset orcomponent; and transmitting, to the device associated with the user,either the presentation of information about the asset or component ofthe physical facility, or a representation of the ticket for initiatingmaintenance of the asset or component of the facility.